How to Define a Metric on a Transaction Date Range

In some cases, transactions do not occur on a single date but span a date range. The date range feature lets you easily calculate metrics for this span of time. This metric definition pattern is very useful for counts of transactions as well as for summing leased areas and remaining costs.

You define metrics by loading the Define Metrics form:

Path: System / Add-In Manager / Define Metrics
URL: http://localhost:8080/archibus/ab-ex-metric-metrics-def.axvw

Example

For example, the metric definition below will count the number of Projects that are active every month. For instance, if the project starts in March and ends in May, the project will be included in the count of projects for March, April, and May.

Field	Value
Metric Title	Projects Active (by month)
Metric Name	proj_ProjectsActive_count_monthly
Metric Description	The total number of active projects.
Business Implication	Indicates the scope of the project management activity including both capital and expensed projects.
Assumptions	Use the Projects application.
Collect: Recurrence	Every Month, on the Last Day of the Month
Collect: From Table	project
Collect: Formula	field:project_id
Collect: Date Field to Filter On	date_start
Collect: Date End Field to Filter On	date_end
Report: Aggregate As	COUNT
Report: Trend Direction	No Significance
Numeric Format	Number
Decimal Places	0 Places
Metric Granularity Assignments	All, by Program

Comments

Collect: Start/End Field to Filter On. These parameters indicate the start and end date to use for the time range filter. If the metric rule is calculating a time interval (e.g. last month), and this time interval overlaps the date range, the metric rule will include the record in that range.